-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RNET-1145, RNET-1143: Fix reading schema from native #3601
Conversation
Pull Request Test Coverage Report for Build 9181337499Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just left a small comment and maybe we should fix those warnings about the non-nullable property
Realm/Realm/Realm.cs
Outdated
{ | ||
ThrowIfDisposed(); | ||
Argument.Ensure(obj.IsManaged, "Only managed objects can be used in FindExisting", nameof(obj)); | ||
var metadata = Metadata[typeof(T).GetMappedOrOriginalName()]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small optimization, but maybe we can move this inside the if?
* main: RNET-1134: Add obfuscation attribute on generated RealmSchema (#3594) Revert "Hide collections in mixed from public API" (#3606) Update to Core 14.7.0 (#3605) RNET-1145, RNET-1143: Fix reading schema from native (#3601) # Conflicts: # .github/templates/test-weaver.yml # .github/workflows/test-weaver.yml
Description
This fixes how we're reading Realm schema from native. It seems that for a few string properties, the default value in Core is empty string, whereas in .NET those are nullable, so our checks for
object_type == null
were failing and we were trying to lookup metadata for primitive properties.Additionally, this adds
Migration.FindInNewRealm
since I saw we're missing that, which made the test easier to write.Fixes #3600
Fixes #3597
TODO